Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent treatment of dates without year #4451

Closed
imotov opened this issue Dec 15, 2013 · 0 comments · Fixed by #4496
Closed

Inconsistent treatment of dates without year #4451

imotov opened this issue Dec 15, 2013 · 0 comments · Fixed by #4496

Comments

@imotov
Copy link
Contributor

imotov commented Dec 15, 2013

When dates are specified without a year, for example: Dec 15 10:00:00 they are treated as dates in 2000 during indexing and range searches except for the upper included bound lte, where they are treated as dates in 1970. Repro: https://gist.github.com/imotov/7978186. Might be related to #2731.

@ghost ghost assigned imotov Dec 18, 2013
@imotov imotov closed this as completed in 56b3941 Jan 7, 2014
brusic pushed a commit to brusic/elasticsearch that referenced this issue Jan 19, 2014
Fixes elastic#4451

Date fields without date (HH:mm:ss, for example) are parsed as time on Jan 1, 1970 UTC. However, before this change partial dates without year (MMM dd HH:mm:ss, for example) were parsed as as days of they year 2000. This change makes all partial dates to be treated based on year 1970. This is breaking change - before this change "Dec 15, 10:00:00" in most cases was parsed (and indexed) as "2000-12-15T10:00:00Z". After this change, it will be consistently parsed and indexed as  "1970-12-15T10:00:00Z"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant